[release-4.18] OCPBUGS-84284: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895 by amitesh1201 · Pull Request #16675 · openshift/console

amitesh1201 · 2026-06-24T07:32:36Z

Summary

CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects
Package: follow-redirects → 1.16.0 (transitive dependency)

Changes

Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json
Updated frontend/yarn.lock

Test Plan

yarn build succeeds

openshift-ci-robot · 2026-06-24T07:32:43Z

@amitesh1201: This pull request references Jira Issue OCPBUGS-84284, which is invalid:

expected dependent Jira Issue OCPBUGS-84285 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects

Package: follow-redirects → 1.16.0 (transitive dependency)

Risk Level: LOW (development-only dependency, not in production)

Impact

Production: NOT AFFECTED (webpack-dev-server and http-server are devDependencies, not deployed)

Development: Potentially affected (local dev server only)

Changes

Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json

Added yarn resolution for follow-redirects@^1.16.0 in dynamic-demo-plugin/package.json

Updated frontend/yarn.lock

Updated dynamic-demo-plugin/yarn.lock

Bumps react-i18next in dynamic-demo-plugin from ^11.7.3 to ^11.12.0 to align with @openshift-console/dynamic-plugin-sdk and fix a yarn PnP link conflict introduced by the lockfile regeneration. The react-i18next bump is not a functional change — react-i18next is a shared singleton module at runtime, so the console host provides the actual instance. This change only fixes the build-time version mismatch between the demo plugin (11.12.0) and the SDK (11.18.6) that caused yarn install to fail with YN0071.

Test Plan

yarn build succeeds (production build)

dynamic-demo-plugin/ installs without errors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-06-24T07:32:45Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: abd79a69-f1de-4943-aede-a8f10f230dc2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands.}

amitesh1201 · 2026-06-24T08:18:18Z

/jira refresh

openshift-ci-robot · 2026-06-24T08:18:22Z

@amitesh1201: This pull request references Jira Issue OCPBUGS-84284, which is invalid:

expected dependent Jira Issue OCPBUGS-84285 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

amitesh1201 · 2026-06-24T08:20:54Z

/test backend

amitesh1201 · 2026-07-01T12:57:04Z

/retest-required

openshift-ci-robot · 2026-07-08T12:38:26Z

@amitesh1201: This pull request references Jira Issue OCPBUGS-84284, which is invalid:

expected dependent Jira Issue OCPBUGS-84285 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Summary

CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects

Package: follow-redirects → 1.16.0 (transitive dependency)

Risk Level: LOW (development-only dependency, not in production)

Impact

Production: NOT AFFECTED (webpack-dev-server and http-server are devDependencies, not deployed)

Development: Potentially affected (local dev server only)

Changes

Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json

Added yarn resolution for follow-redirects@^1.16.0 in dynamic-demo-plugin/package.json

Updated frontend/yarn.lock

Updated dynamic-demo-plugin/yarn.lock

Test Plan

yarn build succeeds (production build)

dynamic-demo-plugin/ installs without errors

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

amitesh1201 · 2026-07-09T05:55:28Z

/test e2e-gcp-console

amitesh1201 · 2026-07-09T12:41:09Z

/test e2e-gcp-console

germanparente · 2026-07-10T09:14:14Z

/label backport-risk-assessed

amitesh1201 · 2026-07-10T10:26:09Z

/retest-required

amitesh1201 · 2026-07-10T17:36:37Z

/retest-required

logonoff · 2026-07-13T13:13:04Z

This yarn.lock looks like it contains a bunch of unrelated changes, please double check this diff

Ack, PRs has been revised to update only required changes. Dynamic-demo-plugin related changes dropped.

logonoff · 2026-07-13T13:13:43Z

/label backport-risk-assessed

amitesh1201 · 2026-07-14T07:02:01Z

/hold

Add follow-redirects resolution to pin >=1.16.0 in frontend/ workspace. Signed-off-by: Amit Yadav <ayadav@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>

amitesh1201 · 2026-07-14T11:33:39Z

/hold cancel
/jira refresh

openshift-ci-robot · 2026-07-14T11:33:44Z

@amitesh1201: This pull request references Jira Issue OCPBUGS-84284, which is invalid:

expected dependent Jira Issue OCPBUGS-84285 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/hold cancel
/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

logonoff

/lgtm

openshift-merge-bot · 2026-07-14T13:21:04Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console

openshift-ci · 2026-07-14T13:21:17Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amitesh1201, logonoff

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~frontend/OWNERS~~ [logonoff]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

amitesh1201 · 2026-07-15T13:38:19Z

/test e2e-gcp-console

prabhapa · 2026-07-17T07:50:04Z

/override ci/prow/e2e-gcp-console
This is infra flake. And the cypress tests that it does has no link to flowredirect lib bump

openshift-ci · 2026-07-17T07:50:10Z

@prabhapa: Overrode contexts on behalf of prabhapa: ci/prow/e2e-gcp-console

Details

In response to this:

/override ci/prow/e2e-gcp-console
This is infra flake. And the cypress tests that it does has no link to flowredirect lib bump

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

openshift-ci · 2026-07-17T07:50:12Z

@amitesh1201: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

amitesh1201 · 2026-07-17T07:58:17Z

/Verified by CI jobs

openshift-ci-robot · 2026-07-17T07:58:28Z

@amitesh1201: This PR has been marked as verified by CI jobs.

Details

In response to this:

/Verified by CI jobs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

amitesh1201 · 2026-07-17T08:02:49Z

/jira refresh

openshift-ci-robot · 2026-07-17T08:02:56Z

@amitesh1201: This pull request references Jira Issue OCPBUGS-84284, which is invalid:

expected dependent Jira Issue OCPBUGS-84285 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

ocp-sustaining-admins · 2026-07-22T05:22:13Z

/jira refresh

openshift-ci-robot · 2026-07-22T05:22:21Z

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-84284, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-84285 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-84285 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-07-22T05:26:38Z

@amitesh1201: Jira Issue Verification Checks: Jira Issue OCPBUGS-84284
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-84284 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary

CVE: CVE-2026-40895 — Information disclosure via custom authentication headers in cross-domain redirects

Package: follow-redirects → 1.16.0 (transitive dependency)

Changes

Added yarn resolution for follow-redirects@^1.16.0 in frontend/package.json

Updated frontend/yarn.lock

Test Plan

yarn build succeeds

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-robot · 2026-07-22T20:29:47Z

Fix included in release 4.18.0-0.nightly-2026-07-22-115907

openshift-ci Bot requested review from Leo6Leo and vojtechszocs June 24, 2026 07:33

amitesh1201 changed the title ~~OCPBUGS-84284: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895~~ [release-4.18] OCPBUGS-84284: Bump follow-redirects to 1.16.0 to fix CVE-2026-40895 Jun 24, 2026

openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 1, 2026

amitesh1201 force-pushed the CVE-2026-40895-follow-redirects-4.18 branch from 848f7d4 to 216fd3d Compare July 8, 2026 12:36

openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 8, 2026

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jul 10, 2026

openshift-ci Bot assigned sanketpathak Jul 10, 2026

logonoff reviewed Jul 13, 2026

View reviewed changes

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 14, 2026

Bump follow-redirects to 1.16.0 to fix CVE-2026-40895

2fd016d

Add follow-redirects resolution to pin >=1.16.0 in frontend/ workspace. Signed-off-by: Amit Yadav <ayadav@redhat.com> Co-authored-by: Cursor <cursoragent@cursor.com>

amitesh1201 force-pushed the CVE-2026-40895-follow-redirects-4.18 branch from 216fd3d to 2fd016d Compare July 14, 2026 09:26

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 14, 2026

logonoff approved these changes Jul 14, 2026

View reviewed changes

openshift-ci Bot assigned logonoff Jul 14, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 14, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 17, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 22, 2026

openshift-merge-bot Bot merged commit 551206f into openshift:release-4.18 Jul 22, 2026
7 checks passed

Uh oh!

Conversation

amitesh1201 commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Test Plan

Uh oh!

openshift-ci-robot commented Jun 24, 2026

Summary

Impact

Changes

Test Plan

Uh oh!

coderabbitai Bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

amitesh1201 commented Jun 24, 2026

Uh oh!

openshift-ci-robot commented Jun 24, 2026

Uh oh!

amitesh1201 commented Jun 24, 2026

Uh oh!

amitesh1201 commented Jul 1, 2026

Uh oh!

openshift-ci-robot commented Jul 8, 2026

Summary

Impact

Changes

Test Plan

Uh oh!

amitesh1201 commented Jul 9, 2026

Uh oh!

amitesh1201 commented Jul 9, 2026

Uh oh!

germanparente commented Jul 10, 2026

Uh oh!

amitesh1201 commented Jul 10, 2026

Uh oh!

amitesh1201 commented Jul 10, 2026

Uh oh!

logonoff Jul 13, 2026

Choose a reason for hiding this comment

Uh oh!

amitesh1201 Jul 14, 2026

Choose a reason for hiding this comment

Uh oh!

logonoff commented Jul 13, 2026

Uh oh!

amitesh1201 commented Jul 14, 2026

Uh oh!

amitesh1201 commented Jul 14, 2026

Uh oh!

openshift-ci-robot commented Jul 14, 2026

Uh oh!

logonoff left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-merge-bot Bot commented Jul 14, 2026

Uh oh!

openshift-ci Bot commented Jul 14, 2026

Uh oh!

amitesh1201 commented Jul 15, 2026

Uh oh!

prabhapa commented Jul 17, 2026

Uh oh!

openshift-ci Bot commented Jul 17, 2026

Uh oh!

openshift-ci Bot commented Jul 17, 2026

Uh oh!

amitesh1201 commented Jul 17, 2026

Uh oh!

openshift-ci-robot commented Jul 17, 2026

Uh oh!

amitesh1201 commented Jul 17, 2026

Uh oh!

openshift-ci-robot commented Jul 17, 2026

Uh oh!

ocp-sustaining-admins commented Jul 22, 2026

amitesh1201 commented Jun 24, 2026 •

edited

Loading

coderabbitai Bot commented Jun 24, 2026 •

edited

Loading